-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: outdated business metric ids #1113
Conversation
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
ACCOUNT_ID_BASED_ENDPOINT("O"), | ||
SIGV4A_SIGNING("P"), | ||
ENDPOINT_OVERRIDE("N"), | ||
ACCOUNT_ID_ENDPOINT("O"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also emit the new ACCOUNT_ID_MODE_PREFERRED
, ACCOUNT_ID_MODE_DISABLED
, ACCOUNT_ID_MODE_REQUIRED
metrics?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we can add that
This comment has been minimized.
This comment has been minimized.
1 similar comment
Affected ArtifactsChanged in size
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: This is an binary-compat breaking change and I see the acknowledge-api-break tag applied to the PR. Why do we think this is safe to release? Isn't this precisely the kind of API change that can bite customers if they're using specific versions of smithy-kotlin different from aws-sdk-kotlin?
Issue #
N/A
Description of changes
The name of these metrics changed, so this PR updates them
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.